Method and apparatus for managing data session in wireless communication system

ABSTRACT

A method performed by a user equipment (UE) in a wireless communication system is provided. The method may include: receiving, from a network entity, information associated with one or more quality of service (QoS) rules; checking the information associated with the one or more QoS rules, for a QoS rule associated with a non-default QoS rule and for the QoS rule with a rule operation different from deleting the QoS rule; in case that the UE is in a narrow band (NB)-N1 mode, the QoS rule is associated with the non-default QoS rule and the rule operation is different from deleting the QoS rule, detecting the QoS rule as an error; and transmitting, to the network entity, a protocol data unit (PDU) session modification request message to delete the detected QoS rule.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 17/205,938filed Mar. 18, 2021, now U.S. Pat. No. 11,638,179 issued Apr. 25, 2023,which is based on and claims priority under 35 U.S.C. § 119(a) to GreatBritain Patent Application No. 2004210.7 filed on Mar. 23, 2020 andGreat Britain Patent Application No. 2004214.9 filed on Mar. 23, 2020,the disclosures of which are herein incorporated by reference in theirentirety.

BACKGROUND 1. Field

The disclosure relates to managing data sessions in a network. Moreparticularly, the disclosure relates to managing Protocol Data Unit(PDU) sessions for Narrowband-Internet of Things (NB-IoT) in 3GPP 5GSession Management (5GSM).

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4th generation (4G) communication systems, efforts havebeen made to develop an improved 5th generation (5G) or pre-5Gcommunication system. The 5G or pre-5G communication system is alsocalled a ‘beyond 4G network’ or a ‘post long term evolution (LTE)system’. The 5G communication system is considered to be implemented inhigher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplishhigher data rates. To decrease propagation loss of the radio waves andincrease the transmission distance, beamforming, massive multiple-inputmultiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna,analog beamforming, and large scale antenna techniques are discussedwith respect to 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud radio access networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,coordinated multi-points (CoMP), reception-end interference cancellationand the like. In the 5G system, hybrid frequency shift keying (FSK) andFeher's quadrature amplitude modulation (FQAM) and sliding windowsuperposition coding (SWSC) as an advanced coding modulation (ACM), andfilter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA),and sparse code multiple access (SCMA) as an advanced access technologyhave been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofeverything (IoE), which is a combination of the IoT technology and thebig data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “security technology” have been demanded forIoT implementation, a sensor network, a machine-to-machine (M2M)communication, machine type communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing information technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, MTC, and M2M communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RAN as theabove-described big data processing technology may also be considered tobe as an example of convergence between the 5G technology and the IoTtechnology.

As described above, various services can be provided according to thedevelopment of a wireless communication system, and thus a method foreasily providing such services is required.

SUMMARY

In accordance an embodiment of the disclosure, a method performed by auser equipment (UE) in a wireless communication system is provided. Themethod may comprise: receiving, from a network entity, informationassociated with one or more quality of service (QoS) rules; checking theinformation associated with the one or more QoS rules, for a QoS ruleassociated with a non-default QoS rule and for the QoS rule with a ruleoperation different from deleting the QoS rule; in case that the UE isin a narrow band (NB)-N1 mode, the QoS rule is associated with thenon-default QoS rule and the rule operation is different from deletingthe QoS rule, detecting the QoS rule as an error; and transmitting, tothe network entity, a protocol data unit (PDU) session modificationrequest message to delete the detected QoS rule.

In accordance an embodiment of the disclosure, a method performed by auser equipment (UE) in a wireless communication system is provided. Themethod may comprise: receiving, from a network entity, informationassociated with one or more quality of service (QoS) flow descriptions;checking the information associated with the one or more QoS flowdescriptions, for a QoS flow description associated with a non-defaultQoS rule and for the QoS flow description with a rule operationdifferent from deleting the QoS flow description; in case that the UE isin a narrow band (NB)-N1 mode, a QoS flow ID (QFI) of the QoS flowdescription is associated with the non-default QoS rule and the ruleoperation is different from deleting the QoS flow description, detectingthe QoS flow description as an error; and transmitting, to the networkentity, a protocol data unit (PDU) session modification request messageto delete the detected QoS flow description.

In accordance an embodiment of the disclosure, a method performed by auser equipment (UE) in a wireless communication system is provided. Themethod may comprise: in case that N3 data transfer is not supported bythe UE, identifying one or more values of an integrity protectionmaximum data rate information element as one or more values indicatingthat the N3 data transfer is not supported by the UE; and transmitting,to a network entity, information associated with the integrityprotection maximum data rate information element.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 illustrates an exemplary coding of an Integrity protectionmaximum data rate IE of type TLV;

FIG. 2 is a block diagram of an exemplary network entity that may beused in certain examples of the present disclosure;

FIG. 3 is a flow chart of a method performed by a user equipmentaccording to an embodiment of the disclosure;

FIG. 4 is a flowchart of a method performed by a user equipmentaccording to another embodiment of the disclosure;

FIG. 5 is a flow chart of a method performed by a user equipmentaccording to another embodiment of the disclosure;

FIG. 6 is a diagram illustrating a user equipment according to anembodiment of the disclosure: and

FIG. 7 is a diagram illustrating a core network entity according toembodiments of the present disclosure.

DETAILED DESCRIPTION

FIGS. 1 through 7 , discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

Throughout the disclosure, the expression “at least one of a, b or c”indicates only a, only b, only c, both a and b, both a and c, both b andc, all of a, b, and c, or variations thereof. Throughout thespecification, a layer (or a layer apparatus) may also be referred to asan entity. Hereinafter, operation principles of the disclosure will bedescribed in detail with reference to accompanying drawings. In thefollowing descriptions, well-known functions or configurations are notdescribed in detail because they would obscure the disclosure withunnecessary details. The terms used in the specification are defined inconsideration of functions used in the disclosure, and can be changedaccording to the intent or commonly used methods of users or operators.Accordingly, definitions of the terms are understood based on the entiredescriptions of the present specification.

For the same reasons, in the drawings, some elements may be exaggerated,omitted, or roughly illustrated. Also, a size of each element does notexactly correspond to an actual size of each element. In each drawing,elements that are the same or are in correspondence are rendered thesame reference numeral.

Advantages and features of the disclosure and methods of accomplishingthe same may be understood more readily by reference to the followingdetailed descriptions of embodiments and accompanying drawings of thedisclosure. The disclosure may, however, be embodied in many differentforms and should not be construed as being limited to the embodimentsset forth herein; rather, these embodiments of the disclosure areprovided so that this disclosure will be thorough and complete, and willfully convey the concept of the disclosure to one of ordinary skill inthe art. Therefore, the scope of the disclosure is defined by theappended claims. Throughout the specification, like reference numeralsrefer to like elements. It will be understood that blocks in flowchartsor combinations of the flowcharts may be performed by computer programinstructions. Because these computer program instructions may be loadedinto a processor of a general-purpose computer, a special-purposecomputer, or another programmable data processing apparatus, theinstructions, which are performed by a processor of a computer oranother programmable data processing apparatus, create units forperforming functions described in the flowchart block(s).

The computer program instructions may be stored in a computer-usable orcomputer-readable memory capable of directing a computer or anotherprogrammable data processing apparatus to implement a function in aparticular manner, and thus the instructions stored in thecomputer-usable or computer-readable memory may also be capable ofproducing manufactured items containing instruction units for performingthe functions described in the flowchart block(s). The computer programinstructions may also be loaded into a computer or another programmabledata processing apparatus, and thus, instructions for operating thecomputer or the other programmable data processing apparatus bygenerating a computer-executed process when a series of operations areperformed in the computer or the other programmable data processingapparatus may provide operations for performing the functions describedin the flowchart block(s).

In addition, each block may represent a portion of a module, segment, orcode that includes one or more executable instructions for executingspecified logical function(s). It is also noted that, in somealternative implementations, functions mentioned in blocks may occur outof order. For example, two consecutive blocks may also be executedsimultaneously or in reverse order depending on functions correspondingthereto.

As used herein, the term “unit” denotes a software element or a hardwareelement such as a field-programmable gate array (FPGA) or anapplication-specific integrated circuit (ASIC), and performs a certainfunction. However, the term “unit” is not limited to software orhardware. The “unit” may be formed so as to be in an addressable storagemedium, or may be formed so as to operate one or more processors. Thus,for example, the term “unit” may include elements (e.g., softwareelements, object-oriented software elements, class elements, and taskelements), processes, functions, attributes, procedures, subroutines,segments of program code, drivers, firmware, micro-codes, circuits,data, a database, data structures, tables, arrays, or variables.

Functions provided by the elements and “units” may be combined into thesmaller number of elements and “units”, or may be divided intoadditional elements and “units”. Furthermore, the elements and “units”may be embodied to reproduce one or more central processing units (CPUs)in a device or security multimedia card. Also, in an embodiment of thedisclosure, the “unit” may include at least one processor. In thefollowing descriptions of the disclosure, well-known functions orconfigurations are not described in detail because they would obscurethe disclosure with unnecessary details.

Hereinafter, for convenience of explanation, the disclosure uses termsand names defined in the 3rd generation partnership project long termevolution (3GPP LTE) standards. However, the disclosure is not limitedto the terms and names, and may also be applied to systems followingother standards.

In the disclosure, an evolved node B (eNB) may be interchangeably usedwith a next-generation node B (gNB) for convenience of explanation. Thatis, a base station (BS) described by an eNB may represent a gNB. In thefollowing descriptions, the term “base station” refers to an entity forallocating resources to a user equipment (UE) and may be usedinterchangeably with at least one of a gNode B, an eNode B, a node B, abase station (BS), a radio access unit, a base station controller (BSC),or a node over a network. The term “terminal” may be usedinterchangeably with a user equipment (UE), a mobile station (MS), acellular phone, a smartphone, a computer, or a multimedia system capableof performing communication functions. However, the disclosure is notlimited to the aforementioned examples. In particular, the disclosure isapplicable to 3GPP new radio (NR) (or 5th generation (5G)) mobilecommunication standards. In the following description, the term eNB maybe interchangeably used with the term gNB for convenience ofexplanation. That is, a base station explained as an eNB may alsoindicate a gNB. The term UE may also indicate a mobile phone, NB-IoTdevices, sensors, and other wireless communication devices.

Herein, the following documents are referenced:

-   -   [1] 3GPPTS 23.501 V16.3.0    -   [2] 3GPPTS 24.501 V16.3.0    -   [3] 3GPPTS 23.502 V16.3.0    -   [4] 3GPP TS 24.301 V16.3.0

Various acronyms and abbreviations used herein are defined at the end ofthis description.

The above documents disclose various operations and procedures,including the following.

Overview of the Integrity protection maximum data rate IE in the PDUSession Establishment Request message

5GS enables the application of integrity protection to the UP of a PDUsession as described in TS 23.501 [1]:

The SMF determines at PDU session establishment a User Plane SecurityEnforcement information for the user plane of a PDU session based on:

subscribed User Plane Security Policy which is part of SM subscriptioninformation received from UDM; and

User Plane Security Policy locally configured per (DNN, S-NSSAI) in theSMF that is used when the UDM does not provide User Plane SecurityPolicy information.

The maximum supported data rate per UE for integrity protection for theDRBs, provided by the UE in the Integrity protection maximum data rateIE during PDU Session Establishment.

As per the above, the UE is required to provide the Integrity protectionmaximum data rate IE in the PDU Session Establishment Request message asspecified in TS 24.501 [2] i.e. this IE is a mandatory IE in the PDUSession Establishment Request as shown below, highlighted in bold andunderline:

TABLE 1 PDU SESSION ESTABLISHMENT REQUEST message content (correspondsto Table 8.3.1.1.1 from [2]) IEI Information Element Type/ReferencePresence Format Length Extended protocol Extended protocol M V 1discriminator discriminator 9.2 PDU session ID PDU session M V 1identity 9.4 PTI Procedure transaction M V 1 identity 9.6 PDU SESSIONESTABLISHMENT Message type M V 1 REQUEST message identity 9.7Integrity protection Integrity protection M V 2 maximum data ratemaximum data rate 9.11.4.7  9- PDU session type PDU session type O TV 19.11.4.11 A- SSC mode SSC mode O TV 1 9.11.4.16 28 5GSM capability 5GSMcapability O TLV 3-15 9.11.4.1 55 Maximum number of Maximum number O TV3 supported packet filters of supported packet filters 9.11.4.9 B-Always-on PDU Always-on PDU session O TV 1 session requested requested9.11.4.4 39 SM PDU DN request SM PDU DN request container O TLV 3-255container 9.11.4.15  7B Extended protocol Extended protocol O TLV-E4-65538 configuration options configuration options 9.11.4.6 66 Headercompression Header compression O TLV 5-257 configuration configuration9.11.4.24 6EXX DS-TT Ethernet port DS-TT Ethernet O TLV 8 MAC addressport MAC address 9.11.4.25 6FYY UE-DS-TT residence UE-DS-TT residencetime O TLV 10 time 9.11.4.26  7C Port management Port managementinformation O TLV-E 4-65538 information container container 9.11.4.27

The support of data transfer over the user plane may also be referred toas N3 data transfer, as indicated by the “N3 data” bit of the 5GMMcapability IE that is defined in [2]. As such, the term “N3 datatransfer” may also mean the transfer of data over the user plane.

Handling of PDU sessions during idle mode inter-RAT mobility to/fromNB-IoT

The NB-IoT RAT is deployed such that the TAIs do not overlap with thosein WB-EUTRA or NRas described in [1]:

Tracking Areas are configured so that they do not contain both NB-IoTand other RATs cells, so when the UE is changing RAT type to or fromNB-IoT while remaining registered with 5GC, the UE will perform theMobility Registration Update procedure, see clause 5.3.2.3. When the UEis changing RAT type to or from NB-IoT and moving between 5GC and EPC,during the Registration, Attach or TAU procedure the RAT type change isdetermined.

PDU session handling is controlled by “PDU Session continuity at interRAT mobility” in the UEs subscription data, which indicates perDNN/S-NSSAI whether to;

-   -   maintain the PDU session,    -   disconnect the PDU session with a reactivation request,    -   disconnect the PDU session without reactivation request, or    -   leave it up to local VPLMN policy    -   when the UE moves between a “broadband” RAT (e.g. NR or        WB-E-UTRAN) and a “narrowband” RAT (NB-IoT).

During PDU session establishment the SMF retrieves the “PDU Sessioncontinuity at inter RAT mobility” subscription information (ifavailable) from the UDM. Local SMF configuration is used if “PDU Sessioncontinuity at inter RAT mobility” is not available for a PDU Session.

The AMF informs the SMF at an inter-RAT idle mobility event, e.g. to orfrom NB-IoT connected to 5GC about the RAT type change in theNsmf_PDUSession_UpdateSMContext message during the Registrationprocedure. Based on this (H-)SMF handles the PDU session according to“PDU session continuity at inter RAT mobility information” subscriptiondata or based on local policy.

NOTE: The “PDU Session continuity at inter RAT mobility” and “PDNcontinuity at inter-RAT mobility” subscription should be the same sothat the PDU sessions/PDN connections are handled the same by both CNtypes.

During inter-RAT idle mode mobility to NB-IoT, if a PDU session has morethan one QoS rule, the SMF shall initiate a PDU session modificationprocedure as described in TS 23.502 [3] to remove any non-default QoSrule, and maintain only the default QoS rule.

As also indicated above, when the UE moves into an NB-IoT coverage orRAT, for which the TAIs are non-overlapping with other RATs, the SMFdetermines whether or to keep the session based on the “PDU Sessioncontinuity at inter RAT mobility” in the UEs subscription data and/orlocal policies. If the session is kept for an NB-IoT device (also knownas UE in NB-N1 mode), the SMF “shall initiate a PDU session modificationprocedure as described in TS 23.502 [3] to remove any non-default QoSrule, and maintain only the default QoS rule”.

In general, during a PDU session modification procedure, the UE checksfor errors in QoS rules. For example, since a PDU session must alwayshave a default QoS rule, then the delete operation on the default QoSrule should not be permitted. Accordingly, the UE will release the PDUsession if such an error occurs as described below from section 6.3.2.4in [2]:

[ . . . SKIP . . . ]

If the PDU SESSION MODIFICATION COMMAND message includes the AuthorizedQoS rules IE, the UE shall process the QoS rules sequentially startingwith the first QoS rule. The UE shall check the QoS rule and the QoSflow description provided in the PDU SESSION MODIFICATION COMMANDmessage for different types of errors as follows:

NOTE 4: If an error is detected in a QoS rule or a QoS flow descriptionwhich requires rejecting the PDU SESSION MODIFICATION COMMAND message,then the Authorized QoS rules IE, the Authorized QoS flow descriptionsIE and the Mapped EPS bearer contexts IE included in the PDU SESSIONMODIFICATION COMMAND message are discarded, if any.

Semantic errors in QoS operations:

When the rule operation is “Modify existing QoS rule and add packetfilters”, “Modify existing QoS rule and replace all packet filters”,“Modify existing QoS rule and delete packet filters” or “Modify existingQoS rule without modifying packet filters” on the default QoS rule andthe DQR bit is set to “the QoS rule is not the default QoS rule”.

When the rule operation is “Modify existing QoS rule and add packetfilters”, “Modify existing QoS rule and replace all packet filters”,“Modify existing QoS rule and delete packet filters” or “Modify existingQoS rule without modifying packet filters” on a QoS rule which is notthe default QoS rule and the DQR bit is set to “the QoS rule is thedefault QoS rule”.

When the rule operation is “Create new QoS rule” and the DQR bit is setto “the QoS rule is the default QoS rule” when there's already a defaultQoS rule with different QoS rule identifier.

When the rule operation is “Delete existing QoS rule” on the default QoSrule.

When the rule operation is “Create new QoS rule”, “Modify existing QoSrule and add packet filters”, “Modify existing QoS rule and replace allpacket filters”, “Modify existing QoS rule and delete packet filters”,or “Modify existing QoS rule without modifying packet filters” and twoor more QoS rules associated with this PDU session would have identicalprecedence values.

When the rule operation is “Modify existing QoS rule and delete packetfilters”, the QoS rule is a QoS rule of a PDU session of IPv4, IPv6,IPv4v6 or Ethernet PDU session type, and the packet filter list in theresultant QoS rule is empty.

When the rule operation is “Create new QoS rule” and there is already anexisting QoS rule with the same QoS rule identifier.

When the rule operation is “Modify existing QoS rule and add packetfilters”, “Modify existing QoS rule and replace all packet filters”,“Modify existing QoS rule and delete packet filters” or “Modify existingQoS rule without modifying packet filters” and the associated QoS ruledoes not exist.

When the rule operation is “Delete existing QoS rule” and there is noexisting QoS rule with the same QoS rule identifier.

When the flow description operation is “Create new QoS flow description”and there is already an existing QoS flow description with the same QoSflow identifier.

When the flow description operation is “Modify existing QoS flowdescription” and the associated QoS flow description does not exist.

When the flow description operation is “Delete existing QoS flowdescription” and there is no existing QoS flow description with the sameQoS flow identifier.

In case 4, the UE shall initiate a PDU session release procedure bysending a PDU SESSION RELEASE REQUEST message with 5GSM cause#83“semantic error in the QoS operation”.

In case 5, if the old QoS rule (i.e. the QoS rule that existed beforethe PDU SESSION MODIFICATION COMMAND message was received) is not thedefault QoS rule, the UE shall not diagnose an error, shall furtherprocess the new request and, if it was processed successfully, shalldelete the old QoS rule which has identical precedence value.Furthermore, after sending the PDU SESSSION MODIFICATION COMPLETE forthe ongoing PDU session modification procedure, the UE shall send a PDUSESSION MODIFICATION REQUEST message with 5GSM cause #83 “semantic errorin the QoS operation” to delete the QoS rule.

In case 5, if the old QoS rule (i.e. the QoS rule that existed beforethe PDU SESSION MODIFICATION COMMAND message was received) is thedefault QoS rule, the UE shall initiate a PDU session release procedureby sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83“semantic error in the QoS operation”.

In case 6, if the QoS rule is not the default QoS rule, after sendingthe PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU sessionmodification procedure, the UE shall send a PDU SESSION MODIFICATIONREQUEST message with 5GSM cause #83 “semantic error in the QoSoperation” to delete the QoS rule.

In case 6, if the QoS rule is the default QoS rule, the UE shallinitiate a PDU session release procedure by sending a PDU SESSIONRELEASE REQUEST message with 5GSM cause #83 “semantic error in the QoSoperation”.

In case 7, if the existing QoS rule is not the default QoS rule and theDQR bit of the new QoS rule is set to “the QoS rule is not the defaultQoS rule”, the UE shall not diagnose an error, further process thecreate request and, if it was processed successfully, delete the old QoSrule. If the existing QoS rule is the default QoS rule or the DQR bit ofthe new QoS rule is set to “the QoS rule is the default QoS rule”, theUE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSMcause #83 “semantic error in the QoS operation”.

In case 9, the UE shall not diagnose an error, further process thedelete request and, if it was processed successfully, consider therespective QoS rule as successfully deleted.

In case 10, the UE shall not diagnose an error, further process thecreate request and, if it was processed successfully, delete the old QoSflow description.

In case 12, the UE shall not diagnose an error, further process thedelete request and, if it was processed successfully, consider therespective QoS flow description as successfully deleted. Otherwise, theUE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSMcause #83 “semantic error in the QoS operation”.

[ . . . SKIP . . . ]

The excerpt above shows that the delete operation on the default QoSrule (case 4 above) will lead to the release of the PDU session i.e. theUE will send the PDU Session Release Request message.

Another error that can occur is that shown in case 3 above, i.e. whenthere is a create operation and the QoS rule is indicated to be adefault QoS rule (i.e. the DQR bit is set to “the QoS rule is thedefault QoS rule”) and the UE already has a default QoS rule. In thiscase, the UE will reject the PDU SESSION MODIFICATION COMMAND messagewith 5GSM cause #83 “semantic error in the QoS operation”.

It is an aim of the disclosure to address, solve and/or mitigate, atleast partly, at least one of the problems and/or disadvantagesassociated with the related art, for example at least one of theproblems and/or disadvantages described herein. It is an aim of thedisclosure to provide at least one advantage over the related art, forexample at least one of the advantages described herein.

The disclosure is defined in the independent claims. Advantageousfeatures are defined in the dependent claims.

Other aspects, advantages, and salient features will become apparent tothose skilled in the art from the following detailed description, takenin conjunction with the annexed drawings, which disclose examples of thedisclosure.

The following description of examples of the present disclosure, withreference to the accompanying drawings, is provided to assist in acomprehensive understanding of the present disclosure, as defined by theclaims. The description includes various specific details to assist inthat understanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the examples described herein canbe made without departing from the scope of the disclosure.

The same or similar components may be designated by the same or similarreference numerals, although they may be illustrated in differentdrawings.

Detailed descriptions of techniques, structures, constructions,functions or processes known in the art may be omitted for clarity andconciseness, and to avoid obscuring the subject matter of the presentdisclosure.

The terms and words used herein are not limited to the bibliographicalor standard meanings, but, are merely used to enable a clear andconsistent understanding of the disclosure.

Throughout the description and claims of this specification, the words“comprise”, “include” and “contain” and variations of the words, forexample “comprising” and “comprises”, means “including but not limitedto”, and is not intended to (and does not) exclude other features,elements, components, integers, steps, processes, operations, functions,characteristics, properties and/or groups thereof.

Throughout the description and claims of this specification, thesingular form, for example “a”, “an” and “the”, encompasses the pluralunless the context otherwise requires. For example, reference to “anobject” includes reference to one or more of such objects.

Throughout the description and claims of this specification, language inthe general form of “X for Y” (where Y is some action, process,operation, function, activity or step and X is some means for carryingout that action, process, operation, function, activity or step)encompasses means X adapted, configured or arranged specifically, butnot necessarily exclusively, to do Y.

Features, elements, components, integers, steps, processes, operations,functions, characteristics, properties and/or groups thereof describedor disclosed in conjunction with a particular aspect, embodiment,example or claim of the present disclosure are to be understood to beapplicable to any other aspect, embodiment, example or claim describedherein unless incompatible therewith.

Certain examples of the present disclosure provide methods, apparatusand systems for managing data sessions in a network. For example,certain examples of the present disclosure provide methods, apparatusand systems for managing PDU sessions for NB-IoT in 3GPP 5GSM. However,the skilled person will appreciate that the present disclosure is notlimited to these examples, and may be applied in any suitable system orstandard, for example one or more existing and/or future generationwireless communication systems or standards.

The following examples are applicable to, and use terminology associatedwith, 3GPP 5G. However, the skilled person will appreciate that thetechniques disclosed herein are not limited to 3GPP 5G. For example, thefunctionality of the various network entities and messages disclosedherein may be applied to corresponding or equivalent entities andmessages in other communication systems or standards. Corresponding orequivalent entities and messages may be regarded as entities andmessages that perform the same or similar role within the network. Theskilled person will also appreciate that the transmission of informationbetween network entities is not limited to the specific form, type ororder of messages described in relation to the examples disclosedherein.

A particular network entity may be implemented as a network element on adedicated hardware, as a software instance running on a dedicatedhardware, and/or as a virtualised function instantiated on anappropriate platform, e.g. on a cloud infrastructure.

The skilled person will appreciate that the present disclosure is notlimited to the specific examples disclosed herein. For example:

The techniques disclosed herein are not limited to 3GPP 5G.

One or more entities in the examples disclosed herein may be replacedwith one or more alternative entities performing equivalent orcorresponding functions, processes or operations.

One or more of the messages in the examples disclosed herein may bereplaced with one or more alternative messages, signals or other type ofinformation carriers that communicate equivalent or correspondinginformation.

One or more further elements or entities may be added to the examplesdisclosed herein.

One or more non-essential elements or entities may be omitted in certainexamples.

The functions, processes or operations of a particular entity in oneexample may be divided between two or more separate entities in analternative example.

The functions, processes or operations of two or more separate entitiesin one example may be performed by a single entity in an alternativeexample.

Information carried by a particular message in one example may becarried by two or more separate messages in an alternative example.

Information carried by two or more separate messages in one example maybe carried by a single message in an alternative example.

The order in which operations are performed and/or the order in whichmessages are transmitted may be modified, if possible, in alternativeexamples.

Certain examples of the present disclosure may be provided in the formof an apparatus/device/network entity configured to perform one or moredefined network functions and/or a method therefor. Certain examples ofthe present disclosure may be provided in the form of a systemcomprising one or more such apparatuses/devices/network entities, and/ora method therefor.

In the techniques of the related art, for example those referred toabove, there occur the following problems.

A problem that the Integrity protection maximum data rate IE isapplicable to the user plane but not all NB-IoT devices support dataover the user plane may occur.

NB-IoT UEs are mandatorily required to support data transfer over thecontrol plane. However, support for data transfer over the user plane isoptional for these UEs.

Even when an NB-IoT device does not support data transfer over the userplane, the current format of the PDU Session Establishment Requestmessage mandates that the UE indicates the supported data rate for whichintegrity protection can be applied on the user plane.

This creates ambiguity in the 5GSM protocol as the UE is mandated toprovide information for a feature that it does not actually support.Moreover, such UEs will be forced to send two additional octets (as theIE is currently 2 octets long) which unnecessarily increases the NASmessage size. This renders it inefficient for NB-IoT devices that are inlow coverage areas, for which the RAN may configure the UE to repeatradio transmissions several times due to the use of coverage enhancement(i.e. when the UE is in a bad coverage). The unnecessary presence of twooctets at the NAS can actually lead to multiple lower layertransmissions if the coverage level is very bad, especially when theentire NAS message cannot fit into one lower layer message fortransmission. The additional two octets at the NAS can actually lead tosegmentation of the NAS message into two parts depending on thetransport block size that the UE is provided with.

A solution is thus needed to avoid a situation in which an NB-IoT UEsends information related to the user plane when the UE does notactually support data transfer over the user plane.

Errors associated with the PDU session modification procedure to deleteall non-default QoS rules after mobility into NB-IoT RAT may be anotherproblem.

As described earlier, when the UE enters NB-IoT RAT or coverage and theSMF decides to maintain an established PDU session for the UE, the SMFperforms a PDU session modification procedure to delete all the QoSrules that are not a default QoS rule but will keep the default ruleonly. This means that if the UE has three PDU sessions, as an example,then for each session there is a need to perform a PDU sessionmodification procedure. If the UE is in a bad coverage, the UE and/orthe RAN may need to retransmit the 5GSM message a few times asconfigured by the RAN, and this increases overall signalling and powerconsumption at the UE.

Moreover, if the UE detects certain errors in the QoS rules when the SMFsends the 5GSM message, e.g. if the deleted QoS rule is a default QoSrule, then the UE will release the PDU session thereby causing moresignalling to be exchanged and that is not power efficient for NB-IoTdevices. This will in turn lead to more signalling to re-establish thePDU session again.

Additionally, as the UE in NB-IoT cannot have any non-default QoS rule,then if the UE receives the PDU Session Modification Command messagewith a QoS rule operation that is the create operation, i.e. to create anew QoS rule, then this should be considered as an error even if thecreate operation itself is not problematic. In this case, the operationon QoS rule should not be anything other than a delete operation for thenon-default QoS rules. The UE is currently not required to check forsuch errors which are typically not considered as an error from a 5GSMprotocol point of view. But since the UE is in NB-IoT, the UE will needto apply different checks to these rules.

Such problems are not yet solved.

Errors associated with a PDU session establishment procedure for a UE inNB-IoT RAT may be another problem.

As described earlier, the UE in NB-IoT RAT can only have a default QoSrule that is associated with a PDU session. As errors can occur duringthe PDU session establishment procedure, it is possible that the PDUSession Establishment Request message can have multiple QoS rules withthe create operation. However, since only one QoS rule can be available(and that is the default QoS rule) then any additional QoS rule with acreate operation should be considered an error. The UE behaviour in thiscase is not yet specified but should be.

Certain examples of the present disclosure address the above problems,for example by providing one or more of the techniques described below.

In certain examples of the present disclosure, a UE which does notsupport transfer of data over the user plane should not send anyinformation about the integrity protection of the user plane. Hence thecorresponding field in the PDU Session Establishment Request message andin the PDU Session Modification Request message should be optional andshould only be sent by UEs that support the transfer of data via theuser plane (also known as N3 data transfer).

Certain examples of the present disclosure provide an efficienttechnique to not use the non-default QoS rules when in NB-IoT RAT, byeither performing a local delete of these rules or by saving them forsubsequent use after mobility out of NB-IoT. Alternatively, if requiredto be deleted explicitly, in certain examples of the present disclosurethe UE may verify the possibility of errors in QoS operations and applya technique to recover from such errors.

Certain examples of the present disclosure will now be described in moredetail.

In an embodiment, handling of the Integrity protection maximum data rateIE in the PDU Session Establishment Request message may be provided.

As indicated above, the NB-IoT UE may not support data transfer over theuser plane. Therefore, it is not necessary that the UE indicates theintegrity protection rate for the user plane that is anyways notsupported. Various examples of the present disclosure provide a numberof solution options to address this problem.

Solution Option 1

In certain examples of the present disclosure, the Integrity protectionmaximum data rate IE should be an optional IE or a conditional IE in thePDU Session Establishment Request message.

The UE, optionally an NB-IoT UE, that does not support N3 data transfer(or transfer of data over the user plane) may not send the Integrityprotection maximum data rate IE in the PDU Session Establishment Requestmessage. Otherwise, the UE supporting N3 data transfer may send the IEin the PDU Session Establishment Request message.

This solution requires that the Integrity protection maximum data rateIE become an optional IE, for example as indicated in Table 2 below:

TABLE 2 PDU SESSION ESTABLISHMENT REQUEST message content with theIntegrity protection maximum data rate IE as optional IEI InformationElement Type/Reference Presence Format Length Extended protocol Extendedprotocol M V 1 discriminator discriminator 9.2 PDU session ID PDUsession M V 1 identity 9.4 PTI Procedure transaction M V 1 identity 9.6PDU SESSION Message type M V 1 ESTABLISHMENT 9.7 REQUEST messageidentity ZZ Integrity protection Integrity protection O or TLV 4 or 3 (e.g. maximum data rate maximum data rate C or TV 7A, or 9.11.4.7 7D ) 9- PDU session type PDU session type O TV 1 9.11.4.11 A- SSC mode SSCmode O TV 1 9.11.4.16 28 5GSM capability 5GSM capability O TLV 3-159.11.4.1 55 Maximum number of Maximum number of O TV 3 supported packetfilters supported packet filters 9.11.4.9 B- Always-on PDU Always-on PDUO TV 1 session requested session requested 9.11.4.4 39 SM PDU DN requestSM PDU DN request O TLV 3-255 container container 9.11.4.15  7B Extendedprotocol Extended protocol O TLV-E 4-65538 configuration optionsconfiguration options 9.11.4.6 66 Header compression Header compressionO TLV 5-257 configuration configuration 9.11.4.24 6EXX DS-TT Ethernetport DS-TT Ethernet O TLV 8 MAC address port MAC address 9.11.4.25 6FYYUE-DS-TT residence UE-DS-TT residence O TLV 10 time time 9.11.4.26  7CPort management Port management O TLV-E 4-65538 information containerinformation container 9.11.4.27

FIG. 1 illustrates an exemplary coding of an Integrity protectionmaximum data rate IE of type TLV.

In certain examples, if the Integrity protection maximum data rate LE isdefined to be of type TLV(type length value), then the IE should becoded as shown in FIG. 1 .

In certain examples, the Integrity protection maximum data rate LEshould only be sent in the PDU Session Modification Request message fora PDN (packet data network) connection established when in S1 mode,after the first inter-system change from S1 mode to N1 mode, the UE isoperating in single-registration mode in the network supporting N26interface, and if the UE supports data transfer over the user plane(i.e. the UE supports N3 data transfer).

In certain examples, the UE which does not support N3 data transfer mayindicate the same to the network so that the SMF is aware that theIntegrity protection maximum data rate field is not sent in the 5GSMmessage.

For example, the indication that the UE can provide may be in one ormore of the following ways:

The UE may include the indication in the ULNAS TRANSPORT message whichcarries the 5GSM message. The indication may be in the form of a new IEwhere the new IE may be of type TV or TLV, or T, or any other type. TheIE may have a value component, optionally in the form of bit positions,where a specific value may be defined for the value component toindicate that N3 data transfer is not supported by the UE. The UE mayoptionally include this indication when sending every 5GSM message.

An existing IE or field in the UL NAS TRANSPORT message may be used forthis purpose as described above. For example, the existing Request typeIE in the UL NAS TRANSPORT message can be used for this purpose. Forexample, the reserved value “11” can be used to mean “initial requestwithout N3 data transfer” where the value indicates that the request isa new request (i.e. to establish a new PDU session) while alsoindicating that the UE does not support N3 data transfer.

A new 5GSM message identity, i.e. a new 5GSM message (e.g. a PDU SessionEstablishment Request for Control Plane Data) may be defined and used.Hence the UE that does not support N3 data transfer may use the new 5GSMmessage (as described herein) to establish a PDU session. This messagewill not contain the Integrity protection maximum data rate IE and the5GSM message will be like the message shown in Table 2 but without theIntegrity protection maximum data rate IE.

The AMF may determine that the UE does not support (or does support) N3data transfer based on the “N3 data” bit (e.g. bit 6 of octet 3) in the5GMM capability IE. For such UEs, when the AMF receives an UL NASTRANSPORT with a new indication that N3 data transfer is not supported(as described above), the AMF may in turn forward this indication to theSMF over the N11 (or Nsmf) reference point (see 3GPP TS 23.501). Notethat the indication on the N11 (or Nsmf) reference point may be in theform of a new value for an existing parameter or may be introduced as anew parameter. Regardless, the indication informs the SMF that N3 datatransfer is not supported by the UE.

When the SMF receives an indication from the AMF (e.g. over the N11 (orNsmf) reference point or using a new parameter or a new value for anexisting parameter) that the UE does not support N3 data transfer, theSMF determines that the PDU Session Establishment Request message doesnot include the Integrity protection maximum data rate field and wouldtherefore expect the 5GSM message to be like the one shown in Table 2but without the Integrity protection maximum data rate IE.

Solution Option 2

In certain examples of the present disclosure, the UE may send Integrityprotection maximum data rate IE optionally as a mandatory IE but set thevalue to a specific value.

In this solution option, the IE is optionally kept as a mandatory IE buta reserved or specific value is defined to be used by a UE, optionallyan NB-IoT UE, that does not support N3 data transfer. As an example, thevalue “011111111” can be used for such UEs that don't support N3 datatransfer and as such these UEs will set the value component of the IE tothis specific value. The value “011111111” may be interpreted as,“NULL”, or “user-plane integrity protection is not supported”, or“user-plane integrity protection is not supported for uplink”, or“user-plane integrity protection is not supported for downlink”, wherebased on the direction being referred to the particular interpretationcan apply. The skilled person will appreciate that this value i.e.“011111111” is to be taken as an example and that any other suitablevalue can be defined for this purpose. Moreover, the skilled person willappreciate that the interpretations provided above are to be taken asexamples and that other interpretations can be defined instead e.g.“control plane only device”, etc.

When the SMF receives this IE in the 5GSM message with a specific valueas described above, the SMF determines that user plane integrityprotection is not supported for this UE and may set the integrityprotection requirement as not needed.

As another alternative of this option, the UE may set the IE to anyvalue.

In certain examples, with any of the alternatives above, when the SMFreceives a PDU Session Establishment Request message, that is forwardedby the AMF, and also receives the Control plane only indication from theAMF, or any of the other indications described herein, then based on thereceived indication (e.g. the Control plane only indication), the SMFdetermines that the integrity protection for the user plane associatedwith this PDU session is not required. The SMF can then ignore thesereceived values.

In an embodiment, handling of QoS rules after inter-RAT mobility into anNB-IoT RAT may be provided.

Solution Option 1

In order to reduce signaling for NB-IoT, in certain examples, uponmobility into NB-IoT RAT, the UE and the SMF may locally delete all theQoS rules that are not the default QoS rules and maintain only thedefault QoS rule. This will avoid the need to initiate a PDU sessionmodification procedure as is currently done. Moreover, the UE and theSMF may optionally set the packet filter that is associated with thedefault QoS rule to a match all filter for the uplink and optionally fordownlink direction such that all the traffic associated with this PDUsession will be mapped or matched to the default QoS rule.

In an alternative example, the UE may verify for additional errors thatare associated with the PDU Session Modification Command message forthis particular case of being in NB-IoT RAT. Since the UE in NB-IoT canonly have one QoS rule and that should be the default QoS rule, then the5GSM message should only contain QoS rules with delete operations sothat all the non-default QoS rules (i.e. all the QoS rules that are notthe default QoS rule) will be deleted as required. To ensure this is thecase, in certain examples the UE may perform the following checks whilein NB-IoT and the PDU Session Modification Command message is received.

In an embodiment, the UE may check if there is a QoS rule with the ruleoperation set to:

“Create new QoS rule” and optionally the DQR bit is not set to “the QoSrule is not the default QoS rule”,

“Modify existing QoS rule and add packet filters”, “Modify existing QoSrule and replace all packet filters”, “Modify existing QoS rule anddelete packet filters” or “Modify existing QoS rule without modifyingpacket filters” and optionally the operation is on the non-default QoSrules.

Alternatively, in an embodiment, the UE for each non-default QoS rule,the UE may check if the operation is different from “Delete existing QoSrule”. If so, the UE may determine that the QoS rule is erroneous andproceed as described herein. Note that this is just another way toachieve the check that is proposed above.

If the above occurs, the UE may, after the completion of the current PDUsession modification procedure, send a PDU Session Modification Requestmessage to delete each of the QoS rule that is not the default QoS rule.

Alternatively, the UE does not diagnose an error and shall locallydelete each QoS rule which is not the default QoS rule.

Alternatively, the UE shall initiate the PDU session release procedure(optionally after the completion of the ongoing PDU session modificationprocedure) by sending the PDU Session Release Request message.

Alternatively, the UE shall reject the PDU session modificationprocedure (i.e. the UE rejects PDU Session Modification Command message)by sending the PDU Session Modification Command Reject message.

In an embodiment, the UE may check if there is a QoS flow descriptionwith the flow description operation set to:

“Create new QoS flow description” for which the QoS flow identifier isnot associated with the QoS flow identifier of the default QoS rule,

“Modify existing QoS flow description” for which the QoS flow identifieris not associated with the QoS flow identifier of the default QoS rule.

Alternatively, in an embodiment, the UE for each QoS flow descriptionwith a QFI that is associated with the non-default QoS rule, the UE maycheck if the operation is different from “Delete existing QoS flowdescription”. If so, the UE may determine that the QoS flow descriptionis erroneous and proceed as described herein. Note that this is justanother way to achieve the check that is proposed above.

If the above occurs, the UE may, after the completion of the current PDUsession modification procedure, send a PDU Session Modification Requestmessage to delete each QoS flow description that has a QFI (QoS FlowIdentifier) which is not the same as the QFI of the default QoS rule.

Alternatively, the UE does not diagnose an error and shall locallydelete each QoS flow description that has a QFI which is not the same asthe QFI of the default QoS rule.

Alternatively, the UE shall initiate the PDU session release procedureby sending the PDU Session Release Request message.

Alternatively, the UE shall reject the PDU session modificationprocedure (i.e. the UE rejects PDU Session Modification Command message)by sending the PDU Session Modification Command Reject message.

In an embodiment, the UE may check if there is at least one mappedEPS(evolved packet system) bearer operation (in the Mapped EPS bearercontexts IE if received) with the operation code set to:

“Create new EPS bearer” and the associated QoS flow identifier (QFI)corresponds to a QoS rule that is not the default QoS rule,

“Modify existing EPS bearer” and the associated QoS flow identifier(QFI) corresponds to a QoS rule that is not the default QoS rule.

Alternatively, in an embodiment, the UE for each Mapped EPS bearercontext with a QFI that is associated with the non-default QoS rule, theUE may check if the operation is different from “Delete existing EPSbearer”. If so, the UE may determine that the Mapped EPS bearer contextis erroneous and proceed as described herein. Note that this is justanother way to achieve the check that is proposed above.

If the above occurs, the UE shall, after the completion of the currentPDU session modification procedure, send a PDU Session ModificationRequest message to delete each mapped EPS bearer context with a QFI thatis not the same as the QFI of the default QoS rule.

Alternatively, the UE does not diagnose an error and shall locallydelete each mapped EPS bearer context with a QFI that is not the same asthe QFI of the default QoS rule.

Alternatively, the UE shall initiate the PDU session release procedureby sending the PDU Session Release Request message.

Alternatively, the UE shall reject the PDU session modificationprocedure (i.e. the UE rejects PDU Session Modification Command message)by sending the PDU Session Modification Command Reject message.

In the examples described above, the UE may detect a few errors asdescribed above. The UE may still take one action in this case asproposed above.

In certain examples, when sending a PDU Session Modification Requestmessage (e.g. to delete at least one QoS rule, or at least one QoS flowdescription, or at least one Mapped EPS bearer context), or when sendinga PDU Session Release Request message, the UE can include any existing5GSM cause (e.g. #83 “semantic error in the QoS operation”) in the 5GSMmessage. Alternatively, the UE shall use a new 5GSM cause set for eachof the errors defined above, or a new 5GSM cause that can be generic andwould apply to all of the cases listed above. As an example, the UE canuse a new 5GSM cause set to “Operation not allowed due to UE in NB-N1mode”.

The skilled person will appreciate that the examples above may also beapplied when the UE is in EPS (i.e. in S1 mode) and the PDN connectionis transferable to N1 mode. As such, the UE should check for the sameerrors when the UE in NB-IoT in S1 mode receives any of the existing ESMmessages, for example that are defined in TS 3GPP 24.301 [4]. Forexample, the UE should check for the same errors listed above in the QoSrules that are received in the Protocol configuration options IE orExtended protocol configuration options IE in the MODIFY EPS BEARERCONTEXT REQUEST message (where the latter is the ESM NAS message that isreceived in S1 mode). Similarly, an existing 5GSM cause can be used whensending an ESM message by the UE (e.g. the MODIFY EPS BEARER CONTEXTACCEPT message) to report an error, for example as described in section6.1.4.1 of [2].

Accordingly, the skilled person will appreciate that all the examplesabove may be applied when the UE is in either N1 mode or S1 mode.

Solution Option 2

In certain examples, the QoS parameters (i.e. QoS rules, QoS flowdescriptions, or Mapped EPS bearer contexts) that are not the defaultQoS rule, or are not associated with the default QoS rule, will belocally saved at the UE and the SMF when the UE enters NB-IoT (or whenthe UE is operating in NB-N1 mode). As the UE may support other RATs,such as WB-EUTRA or NR, then upon mobility from NB-IoT to another RATthe restriction about having only a default QoS rule will be lifted andthe UE can then have QoS rules that are not a default QoS rule and canalso have other associated QoS parameters (e.g. QoS flow descriptions orMapped EPS bearer contexts).

As such, in certain examples of the present disclosure, when the UEenters NB-IoT, the UE should locally save a copy of all the non-defaultQoS parameters (i.e. each QoS rule that is not a default QoS rule andany associated QoS flow description or Mapped EPS bearer context). TheUE in NB-IoT will then only use the default QoS rule and any otherassociated QoS parameter (e.g. QoS flow description or Mapped EPS bearercontext).

Herein, the term “QoS parameters” may refer to any suitable parameters,for example QoS rules, QoS flow descriptions, or Mapped EPS bearercontexts in the examples below.

In certain examples, to save the QoS parameters, the UE may save a QoSparameter context and a corresponding QoS parameter context ID. Forexample, the QoS parameter context and a corresponding QoS parametercontext ID may be in the following form.

In an embodiment, the form may include a list of QoS rule identifier foreach QoS rule.

For each QoS rule, an associated QoS flow description (where theassociation between the QoS rule and the QoS flow description is basedon a QFI) may be indicated.

For each QoS rule, an associated Mapped EPS bearer context (where theassociation between the Mapped EPS bearer context and the QoS flowdescription may be based on a QFI and optionally an EPS bearer identity(ID)) may be indicated.

In certain examples, the Mapped EPS bearer context may be represented inthe form of an EPS bearer ID and all the other EPS related QoSparameters (e.g. TFT, packet filters, etc, for example as defined in [2]and [4]).

In an embodiment, QoS parameter context ID corresponding to each QoSrule identifier may be indicated.

In certain examples, the QoS parameter context ID may be part of thesaved QoS parameter context.

In certain examples, the QoS parameter context may be saved per PDUsession.

Similarly, the SMF may apply similar behavior as described above, notingthat the SMF becomes aware of the UE's mobility into NB-IoT based on anindication from the AMF.

In certain examples, the UE that supports saving locally of the QoSparameters as described above may indicate this support either in the5GMM capability IE or the 5GSM capability IE. For example, a new bitposition in these IEs may be used for this purpose, e.g. “Saving of QoSparameters locally is supported” can be used, or any other suitabledefinition can be used for this purpose.

Similarly, in certain examples the network (e.g. AMF or SMF) mayindicate if this is also supported in the network. For example, the AMFcan indicate if this is supported by defining a similar bit in the 5GSnetwork feature support IE (defined in [2]) that indicates that thenetwork supports and allows the use of this feature. Alternatively, theSMF can indicate that it supports and allows the use of this feature bydefining and using a similar bit in the 5GSM network feature support IE(defined in [2]). The network may indicate whether this is allowed for aUE based on the UE's capability and optionally the subscriptioninformation or local policies in the network.

In certain examples, the UE may operate in the manner described above ifthe network indicates that saving QoS parameters locally is allowed orthe UE operates in this manner by default whenever the UE enters NB-IoT.

Although the QoS parameters are saved locally, certain examples of thepresent disclosure may define a new QoS operation that indicates thesaving of QoS parameters as described above. The operation may becalled, as an example, “Save existing QoS rule”.

In certain examples, the SMF may send a PDU Session Modification Commandmessage to the UE after the SMF receives an indication that the UE hasentered NB-IoT. The SMF may transmit the PDU Session ModificationCommand message to inform the UE to save its QoS parameters. To do so,the SMF may set the QoS operation code to “Save existing QoS rule” foreach of the QoS rule identifier. In certain examples, a similaroperation may be defined for the QoS flow descriptions and the MappedEPS bearer context. Alternatively, by indicating a specific QoS rule tobe saved, the SMF and UE may also save all corresponding QoS parameters.

The use of this operation can also implicitly lead to the UE and SMF touse the default QoS rule only and its corresponding QoS parameters.Hence, when this new operation is used, the recipient saves all the QoSparameters that are currently available for the PDU session and thencontinues to use the default QoS rule and its corresponding QoSparameters as long as the UE is in NB-IoT.

Therefore, for example, when the UE enters NB-IoT, the SMF may send aPDU Session Modification Command message to the UE and set the operationcode to “Save existing QoS rule” for each of the QoS rule identifierthat should be saved. The UE and SMF both may save all the QoSparameters accordingly that correspond to each QoS rule identifier forwhich this operation is used. The UE may then send the PDU SessionModification Complete message. Optionally, the UE may acknowledge thesaving of the QoS parameters locally by including the QoS rule IE andsetting the operation code to “Save existing QoS rule” for each of theQoS rule identifier for each of the QoS rule that has been saved (andoptionally the corresponding QoS parameters that are associated withthat QoS rule).

Alternatively, a new IE with a list of QoS rule identifier can be usedby either the UE or the SMF and the UE or the SMF may include it in a5GSM message to indicate the list of QoS rule identifiers that have beenor should be locally saved.

Alternatively, the UE may be the entity that sends the PDU SessionModification Request message and sets the operation code to “Saveexisting QoS rule” for each of the QoS rule identifier that is saved.The UE may do so after moving into NB-IoT. The network can then respondwith the PDU Session Modification Command message as proposed above.

In certain examples, when the UE moves out of NB-IoT, the UE mayautonomously resume using all saved QoS parameters. The SMF may also dothe same after being notified that the UE has moved out of NB-IoT (e.g.into WB-EUTRA or NR).

In certain examples of the present disclosure, the above techniques mayalso be achieved by defining a new IE instead of using the QoS rules IE.For example, a new Saved QoS parameter context IE may be defined to listthe QoS parameters that have been, or should be, saved. In certainexamples, the IE may contain any combination of the current QoSparameters that are listed above or that are defined in [2].

In an embodiment, handling of QoS rules at the Establishment of a newPDU Session in N1 mode or PDN Connection in S1 mode is provided.

As indicated above, the UE in NB-IoT can only have, for each PDUsession, a default QoS rule only. As such, no other non-QoS rules canexist. However, as errors can occur, the UE should check that this doesnot happen.

Therefore, in certain examples of the present disclosure, when the UE inNB-IoT receives a PDU Session Establishment Accept message, the UEshould check for the following:

In an embodiment, the UE should check if the QoS rules received containthe operation set to “Create new QoS rule”, and optionally the DQR bitis not set to “the QoS rule is not the default QoS rule” (i.e. there isan operation to create a new QoS rule that is not a default QoS rule).

If the above occurs, the UE shall, after the completion of the currentPDU session establishment procedure, send a PDU Session ModificationRequest message to delete each of the QoS rule that is not the defaultQoS rule.

Alternatively, the UE does not diagnose an error and shall locallydelete each QoS rule which is not a default QoS rule. That is, the UElocally deletes any rule that is not a default QoS rule, and does notreport an error to the network.

Alternatively, the UE shall initiate the PDU session release procedureby sending the PDU Session Release Request message. For example, the UEmay use an existing 5GSM cause or a new 5GSM cause as described herein.

The UE should check if the flow description operation (in the QoS flowdescriptions IE) is set to “Create new QoS flow description”, therequest type is “initial request”, and the QFI of the QoS flowdescription is not the same as the QFI that is associated with defaultQoS rule.

If the above occurs, the UE shall, after the completion of the currentPDU session establishment procedure, send a PDU Session ModificationRequest message to delete each QoS flow description that has a QFI whichis not the same as the QFI of the default QoS rule.

Alternatively, the UE does not diagnose an error and shall locallydelete each QoS flow description that has a QFI which is not the same as(or is not associated with) the QFI of the default QoS rule. That is,the UE locally deletes all other additional QoS flow descriptions thathave a QFI which is not the same as the QFI of the default QoS rule. AQoS flow description is associated with a QoS rule by the QFI. Sinceonly a default QoS rule is allowed for each PDU session when the UE isin NB-IoT, then if the QoS flow description has a QFI which is not thesame as the QFI of the default QoS rule the UE should not keep it.Examples of the present disclosure locally delete such QoS flowdescription.

Alternatively, the UE shall initiate the PDU session release procedureby sending the PDU Session Release Request message. For example, the UEmay use an existing 5GSM cause or a new 5GSM cause as described herein.

The UE should check if there is at least one mapped EPS bearer operation(in the Mapped EPS bearer contexts IE if received) with the operationcode set to:

“Create new EPS bearer” and the associated QFI corresponds to a QoS rulethat is not the default QoS rule,

“Modify existing EPS bearer” and the associated QFI corresponds to a QoSrule that is not the default QoS rule.

If the above occurs, the UE shall, optionally after the completion ofthe current 5GSM procedure, send a PDU Session Modification Requestmessage to delete each mapped EPS bearer context with a QFI that is notthe same as the QFI of the default QoS rule.

Alternatively, the UE does not diagnose an error and shall locallydelete each mapped EPS bearer context with a QFI that is not the same as(or is not associated with) the QFI of the default QoS rule. That is,the UE locally deletes each mapped EPS bearer context with a QFI that isnot the same as (or is not associated with) the QFI of the default QoSrule, and does not report an error to the network.

Alternatively, the UE shall initiate the PDU session release procedureby sending the PDU Session Release Request message. For example, the UEmay use an existing 5GSM cause or a new 5GSM cause as described herein.

The above examples may also be applied when the UE is in S1 mode forwhich the UE is proposed to verify the same or equivalent orcorresponding errors on TFTs, QoS rules and QoS flow descriptions duringany ESM procedure.

Summary of Certain Examples of the Present Disclosure

The UE should preferably not send information that is related to anunsupported feature. Sending such information is not only useless forthe network but is also inefficient as it will unnecessarily increasethe message size and potentially increase power consumption when the UEis in low coverage areas. As described above, certain examples of thepresent disclosure provide techniques to avoid sending information thatdoes not apply to the sending UE.

Furthermore, the UE in NB-IoT may receive different QoS rule operations,or QoS flow description operations, or mapped EPS bearer contextoperations to create or modify existing rules, flow descriptions, ormapped EPS bearer contexts, respectively, where the QFI of theseparameters are not associated with the default QoS rule. Such parametersare not allowed to exist for a UE in NB-IoT (since only the default QoSrule can be available for the UE's PDU session) and there are currentlyno means to check for such errors and recover from them. On the otherhand, certain examples of the present disclosure provide techniques torecover from such QoS errors.

In accordance with an example of the present disclosure, there isprovided a method, for a UE, for establishing a data session, the methodcomprising: determining whether to provide an indication of a maximumdata rate for the data session; if it is determined to provide theindication, transmitting, to a network entity, a data sessionestablishment request including the indication; and if it is determinednot to provide the indication, transmitting, to the network entity, adata session establishment request not including the indication.

In accordance with another example of the present disclosure, there isprovided a method, for a UE, for establishing a data session, the methodcomprising: determining whether the UE supports transfer of data overthe user plane; if the UE supports transfer of data over the user plane,transmitting, to a network entity, a data session establishment requestincluding an indication of a maximum data rate for the data session; andif the UE does not support transfer of data over the user plane,transmitting, to the network entity, a data session establishmentrequest including a value (e.g. predetermined value) indicating that theUE does not support transfer of data over the user plane.

In accordance with another example of the present disclosure, there isprovided a method, for a network entity, for establishing a datasession, the method comprising: receiving a data session establishmentrequest; determining whether the data session establishment requestincludes a value (e.g. predetermined value) indicating that a UE doesnot support transfer of data over the user plane, or whether anindication of a maximum data rate for the data session is included inthe data session establishment request: if the data sessionestablishment request includes the value or does not include anindication of a maximum data rate, determining that the UE does notsupport user plane integrity protection and setting an integrityprotection requirement as not needed for the UE.

In accordance with another example of the present disclosure, there isprovided a method, for a UE and/or a first network entity (e.g. an SMFentity), for managing a data session in a network, wherein the datasession is established for the UE and is associated with one or more QoSrules including a default QoS rule, the method comprising: in responseto mobility of the UE from a first RAT into a second RAT (e.g. NB-IoTRAT), deleting, at the UE and/or the first network entity, all QoS rulesexcept for the default QoS rule.

In accordance with another example of the present disclosure, there isprovided a method, for a UE, for managing a data session in a network,wherein the data session is established for the UE and is associatedwith one or more QoS rules including a default QoS rule, the methodcomprising: in response to receiving a data session modification commandfrom a network entity (e.g. an SMF entity) while the UE is in a secondRAT (e.g. NB-IoT RAT), determining whether a condition, based on one ormore QoS parameters (e.g. one or more of QoS rules, QoS flowdescriptions, and mapped EPS bearer contexts) associated with the datasession modification command, is satisfied.

In accordance with another example of the present disclosure, there isprovided a method, for a UE and/or a first network entity (e.g. an SMFentity), for managing a data session in a network, wherein the datasession is established for the UE and is associated with one or more QoSrules including a default QoS rule, the method comprising: in responseto mobility of the UE from a first RAT into a second RAT (e.g. NB-IoTRAT), or in response to receiving a data session modification messageincluding a predetermined indication, saving, by the UE and/or the firstnetwork entity, one or more QoS parameters (e.g. one or more of QoSrules, QoS flow descriptions, and mapped EPS bearer contexts) associatedwith the data session.

In accordance with another example of the present disclosure, there isprovided a method, for a UE, for managing a data session in a network,wherein the data session is established for the UE and is associatedwith one or more QoS rules including a default QoS rule, the methodcomprising: in response to receiving a data session establishment acceptmessage from a network entity (e.g. an SMF entity) while the UE is in asecond RAT (e.g. NB-IoT RAT), determining whether a condition, based onone or more QoS parameters (e.g. one or more of QoS rules, QoS flowdescriptions, and mapped EPS bearer contexts) associated with the datasession establishment accept message, is satisfied.

FIG. 2 is a block diagram of an exemplary network entity or UE that maybe used in examples of the present disclosure. The skilled person willappreciate that a network entity may be implemented, for example, as anetwork element on a dedicated hardware, as a software instance runningon a dedicated hardware, and/or as a virtualized function instantiatedon an appropriate platform, e.g. on a cloud infrastructure.

The entity or UE 200 comprises a processor (or controller) 201, atransmitter 203 and a receiver 205. The receiver 205 is configured forreceiving one or more messages from one or more other network entities,for example as described above. The transmitter 203 is configured fortransmitting one or more messages to one or more other network entities,for example as described above. The processor 201 is configured forperforming one or more operations, for example according to theoperations as described above.

The techniques described herein may be implemented using any suitablyconfigured apparatus and/or system. Such an apparatus and/or system maybe configured to perform a method according to any aspect, embodiment,example or claim disclosed herein. Such an apparatus may comprise one ormore elements, for example one or more of receivers, transmitters,transceivers, processors, controllers, modules, units, and the like,each element configured to perform one or more corresponding processes,operations and/or method steps for implementing the techniques describedherein. For example, an operation/function of X may be performed by amodule configured to perform X (or an X-module). The one or moreelements may be implemented in the form of hardware, software, or anycombination of hardware and software.

It will be appreciated that examples of the present disclosure may beimplemented in the form of hardware, software or any combination ofhardware and software. Any such software may be stored in the form ofvolatile or non-volatile storage, for example a storage device like aROM, whether erasable or rewritable or not, or in the form of memorysuch as, for example, RAM, memory chips, device or integrated circuitsor on an optically or magnetically readable medium such as, for example,a CD, DVD, magnetic disk or magnetic tape or the like.

It will be appreciated that the storage devices and storage media areembodiments of machine-readable storage that are suitable for storing aprogram or programs comprising instructions that, when executed,implement certain examples of the present disclosure. Accordingly,certain examples provide a program comprising code for implementing amethod, apparatus or system according to any example, embodiment, aspectand/or claim disclosed herein, and/or a machine-readable storage storingsuch a program. Still further, such programs may be conveyedelectronically via any medium, for example a communication signalcarried over a wired or wireless connection.

FIG. 3 is a flow chart of a method performed by a user equipmentaccording to an embodiment of the disclosure.

In step 301, in case that N3 data transfer is not supported by the UE,the UE may identify one or more values of an integrity protectionmaximum data rate information element (IE) as one or more valuesindicating that the N3 data transfer is not supported by the UE. Asdescribed above, the N3 data transfer may refer to a support of datatransfer over a user plane. For example, the UE may be in a narrow band(NB)-N1 mode.

For example, the integrity protection maximum data rate informationelement may comprise: a first user plane integrity protection maximumdata rate for an uplink; and a second user plane integrity protectionmaximum data rate for a downlink.

The UE may identify one or more first values of the first user planeintegrity protection maximum data rate as one or more values indicatingthat user-plane integrity protection for the uplink is not supported bythe UE. For example, the one or more first values indicating that theuser-plane integrity protection for the uplink is not supported may beone or more null values.

The UE may identify one or more second values of the second user planeintegrity protection maximum data rate as one or more values indicatingthat user-plane integrity protection for the downlink is not supportedby the UE. For example, the one or more second values indicating thatthe user-plane integrity protection for the downlink is not supportedmay be one or more null values.

In step 303, the UE may transmit, to a network entity, informationassociated with the integrity protection maximum data rate IE. Forexample, the UE may transmit, to the network entity, the informationassociated with the integrity protection maximum data rate IE via a datasession establishment request for indicating the network entity that theUE does not support the N3 data transfer.

FIG. 4 is a flow chart of a method performed by a user equipmentaccording to another embodiment of the disclosure.

In step 401, the UE may receive, from a network entity, informationassociated with one or more quality of service (QoS) rules. For example,the information associated with the one or more QoS rules may betransferred via at least one of a PDU session modification command or aPDU session establishment accept message. Specifically, the UE may be ina narrow band (NB)-N1 mode.

In step 402, the UE may check the information associated with the one ormore QoS rules, for a QoS rule associated with a non-default QoS ruleand for the QoS rule with a rule operation different from deleting theQoS rule.

In step 403, in case that the UE is in NB-N1 mode, the QoS rule isassociated with the non-default QoS rule and a rule operationcorresponding to the QoS rule associated with the non-default QoS ruleis different from deleting the QoS rule, the UE may detect the QoS ruleas an error. For example, in case that the information associated withthe one or more QoS rules is transferred via the PDU sessionestablishment accept message, the rule operation corresponding to theQoS rule may indicate the UE to create the QoS rule, which is thenon-default QoS rule. For example, a default QoS Rule indicator (DQR)bit of the QoS rule may indicate that the QoS rule is the non-defaultQoS rule.

In step 405, the UE may transmit, to the network entity, a protocol dataunit (PDU) session modification request message to delete the detectedQoS rule. For example, the PDU session modification request message maycomprise information associated with a sematic error in a QoS operationfor deleting the detected QoS rule. For example, in case that theinformation associated with the one or more QoS rules is transferred viathe PDU session modification command, the UE may transmit, to thenetwork entity, the PDU session modification request message aftertransmitting a PDU session modification complete message correspondingto the PDU session modification command.

FIG. 5 is a flow chart of a method performed by a user equipmentaccording to another embodiment of the disclosure.

In step 501, the UE may receive, from a network entity, informationassociated with one or more quality of service (QoS) flow descriptions.For example, the information associated with the one or more QoS flowdescriptions may be transferred via at least one of a PDU sessionmodification command or a PDU session establishment accept message.Specifically, the UE may be in a narrow band (NB)-N1 mode.

In step 502, the UE may check the information associated with the one ormore QoS flow descriptions, for a QoS flow description associated with anon-default QoS rule and for the QoS flow description with a ruleoperation different from deleting the QoS flow description.

In step 503, in case that the UE is in the NB-N1 mode, a QoS flow ID(QFI) of the QoS flow description is associated with the non-default QoSrule and a rule operation corresponding to the QoS flow description isdifferent from deleting the QoS flow description associated with thenon-default QoS rule, the UE may detect the QoS flow description as anerror. For example, in case that the information associated with the oneor more QoS flow descriptions is transferred via the PDU sessionestablishment accept message, the rule operation may indicate to createthe QoS flow description with the QFI associated with the non-defaultQoS rule. For example, in case that the information associated with theone or more QoS flow descriptions is transferred via the PDU sessionestablishment accept message, a request type of a PDU session associatedwith the PDU session establishment accept message may be set to aninitial request.

In step 505, the UE may transmit, to the network entity, a protocol dataunit (PDU) session modification request message to delete the detectedQoS flow description. For example, the PDU session modification requestmessage may comprise information associated with a sematic error in aQoS operation for deleting the detected QoS flow description. Forexample, in case that the information associated with the one or moreQoS flow descriptions is transferred via the PDU session modificationcommand, the UE may transmit, to the network entity, the PDU sessionmodification request message after transmitting a PDU sessionmodification complete message corresponding to the PDU sessionmodification command.

FIG. 6 is a diagram illustrating a user equipment according to anembodiment of the disclosure;

Referring to the FIG. 6 , the UE 600 may include a processor 610, atransceiver 620 and a memory 630. However, all of the illustratedcomponents are not essential. The UE 600 may be implemented by more orless components than those illustrated in the FIG. 6 . In addition, theprocessor 610 and the transceiver 620 and the memory 630 may beimplemented as a single chip according to another embodiment.

The aforementioned components will now be described in detail.

The processor 610 may include one or more processors or other processingdevices that control the proposed function, process, and/or method.Operation of the UE 600 may be implemented by the processor 610.

The transceiver 620 may be connected to the processor 610 and transmitand/or receive a signal. In addition, the transceiver 620 may receivethe signal through a wireless channel and output the signal to theprocessor 610. The transceiver 620 may transmit the signal output fromthe processor 610 through the wireless channel.

The memory 630 may store the control information or the data included ina signal obtained by the UE 600. The memory 630 may be connected to theprocessor 310 and store at least one instruction or a protocol or aparameter for the proposed function, process, and/or method. The memory630 may include read-only memory (ROM) and/or random access memory (RAM)and/or hard disk and/or CD-ROM and/or DVD and/or other storage devices.

According to an embodiment of the disclosure, in case that N3 datatransfer is not supported by the UE, the processor 610 is configured to:identify one or more values of an integrity protection maximum data rateinformation element as one or more values indicating that the N3 datatransfer is not supported by the UE; and transmit, to a network entityvia the transceiver 620, information associated with the integrityprotection maximum data rate information element.

In an embodiment, the integrity protection maximum data rate informationelement may comprise: a first user plane integrity protection maximumdata rate for an uplink; and a second user plane integrity protectionmaximum data rate for a downlink.

In an embodiment, the processor 610 is further configured to identifyone or more first values of the first user plane integrity protectionmaximum data rate as one or more values indicating that user-planeintegrity protection for the uplink is not supported by the UE.

In an embodiment, the processor 610 is further configured to determineone or more second values of the second user plane integrity protectionmaximum data rate as one or more values indicating that user-planeintegrity protection for the downlink is not supported by the UE.

According to another embodiment of the disclosure, the processor 610 isconfigured to: receive, from a network entity via the transceiver 620,information associated with one or more quality of service (QoS) rules;check the information associated with the one or more QoS rules, for aQoS rule associated with a non-default QoS rule and for the QoS rulewith a rule operation different from deleting the QoS rule; in case thatthe UE 600 is in a narrow band (NB)-N1 mode, the QoS rule is associatedwith the non-default QoS rule and the rule operation is different fromdeleting the QoS rule, detect the QoS rule as an error; and transmit, tothe network entity via the transceiver 620, a protocol data unit (PDU)session modification request message to delete the detected QoS rule.

In an embodiment, the information associated with the one or more QoSrules may be transferred via a PDU session modification command

In an embodiment, the information associated with the one or more QoSrules may be transferred via a PDU session establishment accept message.

In an embodiment, in case that the information associated with the oneor more QoS rules is transferred via the PDU session establishmentaccept message.

In an embodiment, the rule operation may indicate to create the QoS ruleassociated with the non-default QoS rule.

In an embodiment, a default QoS Rule indicator (DQR) bit of the QoS ruleindicates that the QoS rule may be the non-default QoS rule.

In an embodiment, the PDU session modification request message maycomprise information associated with a sematic error in a QoS operation.

In an embodiment, the processor 610 is further configured to transmit,to the network entity via the transceiver 620, the PDU sessionmodification request message after transmitting a PDU sessionmodification complete message corresponding to the PDU sessionmodification command.

According to another embodiment of the disclosure, the processor 610 isconfigured to: receive, from a network entity via the transceiver 620,information associated with one or more quality of service (QoS) flowdescriptions; check the information associated with the one or more QoSflow descriptions, for a QoS flow description associated with anon-default QoS rule and for the QoS flow description with a ruleoperation different from deleting the QoS flow description; in case thatthe UE is in a narrow band (NB)-N1 mode, a QoS flow ID (QFI) of the QoSflow description is associated with the non-default QoS rule and therule operation is different from deleting the QoS flow description,detect the QoS flow description as an error; and transmit, to thenetwork entity via the transceiver 620, a protocol data unit (PDU)session modification request message to delete the detected QoS flowdescription.

In an embodiment, the information associated with the one or more QoSflow descriptions is transferred via a PDU session modification command.

In an embodiment, the information associated with the one or more QoSflow descriptions is transferred via a PDU session establishment acceptmessage.

In an embodiment, in case that the information associated with the oneor more QoS flow descriptions is transferred via the PDU sessionestablishment accept message, the rule operation corresponding to theQoS flow description may indicate to create the QoS flow descriptionassociated with the non-default QoS flow description.

In an embodiment, a request type of a PDU session associated with thePDU session establishment accept message may be set to an initialrequest.

In an embodiment, the PDU session modification request message maycomprise information associated with a sematic error in a QoS operation.

In an embodiment, the processor 610 is further configured to transmit,to the network entity via the transceiver 620, the PDU sessionmodification request message after transmitting a PDU sessionmodification complete message corresponding to the PDU sessionmodification command.

FIG. 7 is a diagram illustrating a core network entity according toembodiments of the present disclosure.

The network entity described above may correspond to the core networkentity 700.

Referring to the FIG. 7 , the core network entity 700 may include aprocessor 710, a transceiver 720 and a memory 730. However, all of theillustrated components are not essential. The core network entity 700may be implemented by more or less components than those illustrated inFIG. 7 . In addition, the processor 710 and the transceiver 720 and thememory 730 may be implemented as a single chip according to anotherembodiment.

The aforementioned components will now be described in detail.

The transceiver 720 may provide an interface for performingcommunication with other devices in a network. That is, the transceiver720 may convert a bitstream transmitted from the core network entity 700to other devices to a physical signal and covert a physical signalreceived from other devices to a bitstream. That is, the transceiver 720may transmit and receive a signal. The transceiver 720 may be referredto as modem, transmitter, receiver, communication unit and communicationmodule. The transceiver 720 may enable the core network entity 700 tocommunicate with other devices or system through backhaul connection orother connection method.

The memory 730 may store a basic program, an application program,configuration information for an operation of the core network entity700. The memory 430 may include volatile memory, non-volatile memory anda combination of the volatile memory and the non-volatile memory. Thememory 730 may provide data according to a request from the processor710.

The processor 710 may control overall operations of the core networkentity 400. For example, the processor 710 may transmit and receive asignal through the transceiver 720. The processor 710 may include atleast one processor. The processor 710 may control the core networkentity 400 to perform operations according to embodiments of the presentdisclosure.

The processor 710 is configured to: in case that N3 data transfer is notsupported by a UE, receive, from the UE via the transceiver 720,information associated with the integrity protection maximum data rateinformation element, wherein one or more value components of theintegrity protection maximum data rate information element include oneor more values indicating that the N3 data transfer is not supported bythe UE, wherein the UE is in a narrow band(NB)-N1 mode.

The processor 710 is configured to: transmit, to a UE in a NB-N1 modevia the transceiver 720, information associated with one or more qualityof service (QoS) rules; and receive, from the UE via the transceiver720, a protocol data unit (PDU) session modification request message todelete a QoS rule detected by the UE, wherein in case that the QoS rule,among the one or more QoS rules, is associated with a non-default QoSrule and a rule operation corresponding to the QoS rule is differentfrom deleting the QoS rule, the QoS rule is detected as an error.

The processor 710 is configured to: transmit, to a UE in a NB-N1 modevia the transceiver 720, information associated with one or more qualityof service (QoS) flow descriptions; and receive from the UE via thetransceiver 720, a protocol data unit (PDU) session modification requestmessage to delete a QoS flow description detected by the UE, wherein incase that a QoS flow ID (QFI) of the QoS flow description is associatedwith a non-default QoS rule and a rule operation corresponding to theQoS flow description is different from deleting the QoS flowdescription, the QoS flow description is detected as an error.

According to an embodiment of the disclosure, a method, for a UE, forestablishing a data session may comprise: determining whether to providean indication of a maximum data rate for the data session; if it isdetermined to provide the indication, transmitting, to a network entity,a data session establishment request including the indication; and if itis determined not to provide the indication, transmitting, to thenetwork entity, a data session establishment request not including theindication.

In an embodiment, wherein the determining comprises: determining toprovide the indication if the UE supports transfer of data over the userplane (e.g. for uplink and/or for downlink); and determining not toprovide the indication if the UE does not support transfer of data overthe user plane (e.g. for uplink and/or for downlink).

In an embodiment, wherein the determining comprises determining toprovide the indication when in S1 mode, after the first inter-systemchange from S1 mode to N1 mode, the UE is operating insingle-registration mode in the network supporting N26 interface, and ifthe UE supports data transfer over the user plane (i.e. the UE supportsN3 data transfer).

In an embodiment, wherein the indication is of format “TLV”, and whereinthe indication comprises a data structure including: (i) a first portion(e.g. first octet) containing an identifier (e.g. an Integrityprotection maximum data rate IEI), (ii) a second portion (e.g. secondoctet) containing a length of the indication (e.g. length of theintegrity protection maximum data rate contents), (iii) a third portion(e.g. third octet) containing a maximum data rate per UE for uplink(e.g. maximum data rate per UE for user-plane integrity protection foruplink), and (iv) a fourth portion (e.g. fourth octet) containing amaximum data rate per UE for downlink (e.g. maximum data rate per UE foruser-plane integrity protection for downlink).

In an embodiment, wherein transmitting the data session establishmentrequest not including the indication comprises transmitting the datasession establishment request including a value (e.g. predeterminedvalue) indicating that the UE does not support transfer of data over theuser plane.

According to an embodiment of the disclosure, a method, for a UE, forestablishing a data session, may comprise: determining whether the UEsupports transfer of data over the user plane; if the UE supportstransfer of data over the user plane, transmitting, to a network entity,a data session establishment request including an indication of amaximum data rate for the data session; and if the UE does not supporttransfer of data over the user plane, transmitting, to the networkentity, a data session establishment request including a value (e.g.predetermined value) indicating that the UE does not support transfer ofdata over the user plane.

In an embodiment, wherein: the data session is a PDU session, theindication comprises an Integrity protection maximum data rate IE, andthe data session establishment request comprises a PDU SessionEstablishment Request message.

According to an embodiment of the disclosure, a method, for a networkentity, for establishing a data session may comprise: receiving a datasession establishment request; determining whether the data sessionestablishment request includes a value (e.g. predetermined value)indicating that a UE does not support transfer of data over the userplane, or whether an indication of a maximum data rate for the datasession is included in the data session establishment request; if thedata session establishment request includes the value or does notinclude an indication of a maximum data rate, determining that the UEdoes not support user plane integrity protection.

In an embodiment, the method may further comprise: forwarding, to asecond network entity, the data session establishment request; andtransmitting, to the second network entity, an indication (e.g. controlplane only indication) that the UE does not support transfer of dataover the user plane, whereby the second network entity (i) determinesthat integrity protection for the user plane associated with the datasession is not required based on the indication that the UE does notsupport transfer of data over the user plane, and (ii) sets an integrityprotection requirement as not needed for the UE.

According to an embodiment of the disclosure, a method, for a UE and/ora first network entity (e.g. an SMF entity), for managing a data sessionin a network, wherein the data session is established for the UE and isassociated with one or more QoS rules including a default QoS rule, themethod may comprise: in response to mobility of the UE from a first RATinto a second RAT (e.g. NB-IoT RAT), deleting, at the UE and/or thefirst network entity, all QoS rules except for the default QoS rule.

In an embodiment, the method may further comprise setting a packetfilter associated with the default QoS rule to match all filter for theuplink (and optionally for the downlink), whereby all traffic associatedwith the data session is mapped to the default QoS rule.

According to an embodiment of the disclosure, a method, for a UE, formanaging a data session in a network, wherein the data session isestablished for the UE and is associated with one or more QoS rulesincluding a default QoS rule, the method may comprise: in response toreceiving a data session modification command from a network entity(e.g. an SMF entity) while the UE is in a second RAT (e.g. NB-IoT RAT),determining whether a condition, based on one or more QoS parameters(e.g. one or more of QoS rules, QoS flow descriptions, and mapped EPSbearer contexts) associated with the data session modification command,is satisfied.

In an embodiment, wherein the condition comprises: there is a QoS rulespecified in the data session modification command with a rule operationset to: “create new QoS rule” (and optionally the QoS rule is not thedefault QoS rule); and/or “modify existing QoS rule” (and optionally theoperation is on a non-default QoS rule).

In an embodiment, the method may further comprise one or more of: if thecondition is satisfied, after completing data session modificationaccording to the data session modification command, transmitting a datasession modification request message to delete each QoS rule that is notthe default QoS rule; if the condition is satisfied, deleting each QoSrule that is not a default QoS rule without reporting an error to thenetwork; and if the condition is satisfied, optionally after completingdata session modification according to the data session modificationcommand, transmitting a data session release request message to initiatea data session release procedure.

In an embodiment, wherein the condition comprises: there is a QoS flowdescription specified in the data session modification command with aflow description operation set to: “create new QoS flow description”(and optionally the QoS flow identifier is not associated with the QoSflow identifier of the default QoS rule); and/or “modify existing QoSflow description” (and optionally the QoS flow identifier is notassociated with the QoS flow identifier of the default QoS rule).

In an embodiment, the method may further comprise one or more of: if thecondition is satisfied, after completing data session modificationaccording to the data session modification command, transmitting a datasession modification request message to delete each QoS flow descriptionthat has a QFI that is not the same as the QFI of the default QoS rule;if the condition is satisfied, deleting, at the UE, each QoS flowdescription that has a QFI that is not the same as the QFI of thedefault QoS rule, without reporting an error to the network; and if thecondition is satisfied, transmitting a data session release requestmessage to initiate a data session release procedure.

In an embodiment, wherein the condition comprises: there is at least onemapped EPS bearer operation with the operation code set to: “create newEPS bearer” (and optionally the associated QFI corresponds to a QoS rulethat is not the default QoS rule); and/or “modify existing EPS bearer”(and optionally the associated QFI corresponds to a QoS rule that is notthe default QoS rule).

In an embodiment, the method may further comprise one or more of: if thecondition is satisfied, after completing data session modificationaccording to the data session modification command, transmitting a datasession modification request message to delete each mapped EPS bearercontext with a QFI that is not the same as the QFI of the default QoSrule; if the condition is satisfied, deleting, at the UE, each mappedEPS bearer context with a QFI that is not the same as the QFI of thedefault QoS rule, without reporting an error to the network; and if thecondition is satisfied, transmitting a data session release requestmessage to initiate a data session release procedure.

In an embodiment, wherein the data session modification request messagecomprises information (e.g. generic or scenario-specific) indicating thereason for the data session modification request.

According to an embodiment of the disclosure, a method, for a UE and/ora first network entity (e.g. an SMF entity), for managing a data sessionin a network, wherein the data session is established for the UE and isassociated with one or more QoS rules including a default QoS rule, themethod may comprise: in response to mobility of the UE from a first RATinto a second RAT (e.g. NB-IoT RAT), or in response to receiving a datasession modification message including a predetermined indication,saving, by the UE and/or the first network entity, one or more QoSparameters (e.g. one or more of QoS rules, QoS flow descriptions, andmapped EPS bearer contexts) associated with the data session.

In an embodiment, the method may further comprise using, for the datasession, the default QoS rule and any QoS parameters associated with thedefault QoS rule.

In an embodiment, wherein saving the QoS parameters comprises saving (i)the default QoS rule and QoS parameters associated with the default QoSrule, and (ii) one or more QoS parameters that are not the default QoSrule or are not associated with the default QoS rule.

In an embodiment, wherein saving the QoS parameters comprises saving aQoS parameter context and a corresponding QoS parameter context ID.

In an embodiment, wherein saving the QoS parameters comprises saving aQoS parameter context per data session.

In an embodiment, wherein the QoS parameter context and thecorresponding QoS parameter context ID comprises: a list of QoS ruleidentifiers for each QoS rule and: for each QoS rule, an associated QoSflow description; for each QoS rule, an associated Mapped EPS bearercontext; and a QoS parameter context ID corresponding to each QoS ruleidentifier.

In an embodiment, the method may further comprise signalling, by the UEand/or the first network entity, support for saving QoS parameters.

In an embodiment, the method may further comprise in response tomobility of the UE from the second RAT into a RAT different from thesecond RAT, retrieving the saved QoS parameters, and using the retrievedQoS parameters for the data session.

According to an embodiment of the disclosure, a method, for a UE, formanaging a data session in a network, wherein the data session isestablished for the UE and is associated with one or more QoS rulesincluding a default QoS rule, the method may comprise: in response toreceiving a data session establishment accept message from a networkentity (e.g. an SMF entity) while the UE is in a second RAT (e.g. NB-IoTRAT), determining whether a condition, based on one or more QoSparameters (e.g. one or more of QoS rules, QoS flow descriptions, andmapped EPS bearer contexts) associated with the data sessionestablishment accept message, is satisfied.

In an embodiment, wherein the condition comprises: there is a QoS rulespecified in the data session establishment accept message with a ruleoperation set to “create new QoS rule” (and optionally the QoS rule isnot the default QoS rule).

In an embodiment, the method may further comprise one or more of: if thecondition is satisfied, after completing data session establishment,transmitting a data session modification request message to delete eachQoS rule that is not the default QoS rule; if the condition issatisfied, deleting each QoS rule that is not the default QoS rulewithout reporting an error to the network; and if the condition issatisfied, transmitting a data session release request message toinitiate a data session release procedure.

In an embodiment, wherein the condition comprises: (i) there is a QoSflow description specified in the data session establishment acceptmessage with a flow description operation set to “create new QoS flowdescription”, (ii) the request type is “initial request”, and (iii) theQFI of the QoS flow description is not the same as the QFI associatedwith the default QoS rule.

In an embodiment, the method may further comprise one or more of: if thecondition is satisfied, after completing data session establishment,transmitting a data session modification request message to delete eachQoS flow description that has a QFI that is not the same as the QFI ofthe default QoS rule; if the condition is satisfied, deleting, at theUE, each QoS flow description that has a QFI that is not the same as theQFI of the default QoS rule, without reporting an error to the network:and if the condition is satisfied, transmitting a data session releaserequest message to initiate a data session release procedure.

In an embodiment, wherein the condition comprises: there is at least onemapped EPS bearer operation with the operation code set to: “create newEPS bearer” (and optionally the associated QFI corresponds to a QoS rulethat is not the default QoS rule); and/or “modify existing EPS bearer”(and optionally the associated QFI corresponds to a QoS rule that is notthe default QoS rule).

In an embodiment, the method may further comprise one or more of: if thecondition is satisfied, after completing data session establishment,transmitting a data session modification request message to delete eachmapped EPS bearer context with a QFI that is not the same as the QFI ofthe default QoS rule; if the condition is satisfied, deleting, at theUE, each mapped EPS bearer context with a QFI that is not the same asthe QFI of the default QoS rule, without reporting an error to thenetwork; and if the condition is satisfied, transmitting a data sessionrelease request message to initiate a data session release procedure.

According to an embodiment of the disclosure, A UE or network entityconfigured to operate according to a method of any preceding claim isdisclosed.

According to an embodiment of the disclosure, a network comprising a UEand/or a network entity is disclosed.

According to an embodiment of the disclosure, a computer programcomprising instructions which, when the program is executed by acomputer or processor, cause the computer or processor to carry out themethod is disclosed.

According to an embodiment of the disclosure, a computer orprocessor-readable data carrier having stored thereon a computer programis disclosed.

According to an embodiment of the disclosure, a method performed by auser equipment (UE) in a wireless communication system is provided. Themethod may comprise: in case that N3 data transfer is not supported bythe UE, identifying one or more values of an integrity protectionmaximum data rate information element as one or more values indicatingthat the N3 data transfer is not supported by the UE; and transmitting,to a network entity, information associated with the integrityprotection maximum data rate information element.

In an embodiment, wherein the integrity protection maximum data rateinformation element may comprise: a first user plane integrityprotection maximum data rate for an uplink; and a second user planeintegrity protection maximum data rate for a downlink.

In an embodiment, wherein the identifying of the one or more valuecomponents of the integrity protection maximum data rate informationelement may comprise: identifying or more first values of the first userplane integrity protection maximum data rate as one or more valuesindicating that a user-plane integrity protection for the uplink is notsupported by the UE.

In an embodiment, wherein the identifying of the one or more values ofthe integrity protection maximum data rate information element maycomprise: identifying one or more second values of the second user planeintegrity protection maximum data rate as one or more values indicatingthat user-plane integrity protection for the downlink is not supportedby the UE.

According to an embodiment of the disclosure, a method performed by auser equipment (UE) in a wireless communication system is provided. Themethod may comprise: receiving, from a network entity, informationassociated with one or more quality of service (QoS) rules; checking theinformation associated with the one or more QoS rules, for a QoS ruleassociated with a non-default QoS rule and for the QoS rule with a ruleoperation different from deleting the QoS rule; in case that the UE isin a narrow band (NB)-N1 mode, the QoS rule is associated with thenon-default QoS rule and the rule operation is different from deletingthe QoS rule, detecting the QoS rule as an error; and transmitting, tothe network entity, a protocol data unit (PDU) session modificationrequest message to delete the detected QoS rule.

In an embodiment, wherein the information associated with the one ormore QoS rules is transferred via a PDU session modification command.

In an embodiment, wherein the information associated with the one ormore QoS rules is transferred via a PDU session establishment acceptmessage.

In an embodiment, wherein the rule operation corresponding to the QoSrule may indicate to create the QoS rule associated with the non-defaultQoS rule.

In an embodiment, wherein the UE is in NB-N1 mode.

In an embodiment, wherein a default QoS Rule indicator (DQR) bit of theQoS rule indicates that the QoS rule is the non-default QoS rule.

In an embodiment, wherein the PDU session modification request messagemay comprise information associated with a sematic error in a QoSoperation.

In an embodiment, wherein the transmitting of the PDU sessionmodification request message may comprise: transmitting, to the networkentity, the PDU session modification request message after transmittinga PDU session modification complete message corresponding to the PDUsession modification command.

According to an embodiment of the disclosure, a method performed by auser equipment (UE) in a wireless communication system is provided. Themethod may comprise: receiving, from a network entity, informationassociated with one or more quality of service, QoS, flow descriptions;checking the information associated with the one or more QoS flowdescriptions, for a QoS flow description associated with a non-defaultQoS rule and for the QoS flow description with a rule operationdifferent from deleting the QoS flow description; in case that the UE isin a narrow band (NB)-N1 mode, a QoS flow ID (QFI) of the QoS flowdescription is associated with the non-default QoS rule and the ruleoperation is different from deleting the QoS flow description, detectingthe QoS flow description as an error; and transmitting, to the networkentity, a protocol data unit (PDU) session modification request messageto delete the detected QoS flow description.

In an embodiment, wherein the information associated with the one ormore QoS flow descriptions is transferred via a PDU, sessionmodification command.

In an embodiment, wherein the information associated with the one ormore QoS flow descriptions is transferred via a PDU sessionestablishment accept message.

In an embodiment, wherein the rule operation corresponding to the QoSflow description indicates to create the QoS flow description associatedwith the non-default QoS flow description.

In an embodiment, wherein the UE is in NB-N1 mode.

In an embodiment, wherein a request type of a PDU session associatedwith the PDU session establishment accept message is set to an initialrequest.

In an embodiment, wherein the PDU session modification request messagecomprises information associated with a sematic error in a QoSoperation.

In an embodiment, wherein the transmitting of the PDU sessionmodification request message comprises: transmitting, to the networkentity, the PDU session modification request message after transmittinga PDU session modification complete message corresponding to the PDUsession modification command.

According to an embodiment of the disclosure, a user equipment (UE) in awireless communication is provided. The UE may comprise a transceiverand at least one processor configured to: in case that N3 data transferis not supported by the UE, identify one or more values of an integrityprotection maximum data rate information element as one or more valuesindicating that the N3 data transfer is not supported by the UE; andtransmit, to a network entity via the transceiver, informationassociated with the integrity protection maximum data rate informationelement.

According to an embodiment of the disclosure, a user equipment (UE) in awireless communication system is provided. The UE may comprise atransceiver and at least one processor configured to: receive, from anetwork entity via the transceiver, information associated with one ormore quality of service (QoS) rules; check the information associatedwith the one or more QoS rules, for a QoS rule associated with anon-default QoS rule and for the QoS rule with a rule operationdifferent from deleting the QoS rule; in case that the UE is in a narrowband (NB)-N1 mode, the QoS rule is associated with the non-default QoSrule and a rule operation is different from deleting the QoS rule,detect the QoS rule as an error; and transmit, to the network entity viathe transceiver, a protocol data unit (PDU) session modification requestmessage to delete the detected QoS rule.

According to an embodiment of the disclosure, a user equipment (UE) in awireless communication system is provided. The UE may comprise atransceiver and at least one processor configured to: receive, from anetwork entity via the transceiver, information associated with one ormore quality of service (QoS) flow descriptions; check the informationassociated with the one or more QoS flow descriptions, for a QoS flowdescription associated with a non-default QoS rule and for the QoS flowdescription with a rule operation different from deleting the QoS flowdescription; in case that the UE is in a narrow band (NB)-N1 mode, a QoSflow ID (QFI) of the QoS flow description is associated with thenon-default QoS rule and a rule operation is different from deleting theQoS flow description, detect the QoS flow description as an error; andtransmit, to the network entity via the transceiver, a protocol dataunit (PDU) session modification request message to delete the detectedQoS flow description, wherein the UE is in a narrow band (NB)-N1 mode.

Although the present disclosure has been described with variousembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method performed by a network entity in awireless communication system, the method comprising: transmitting, to auser equipment (UE), information associated with one or more quality ofservice (QoS) rules, wherein the information associated with the one ormore QoS rules indicates a rule operation corresponding to a QoS ruleand whether the QoS rule is a default QoS rule, and wherein in case thatthe UE is in a narrow band (NB)-N1 mode, the rule operation is differentfrom deleting existing QoS rule and the QoS rule is not the default QoSrule, the QoS rule is detected as an error; and receiving, from the UE,a protocol data unit (PDU) session modification request message todelete the detected QoS rule.
 2. The method of claim 1, wherein theinformation associated with the one or more QoS rules is transferred viaa PDU session modification command.
 3. The method of claim 1, whereinthe information associated with the one or more QoS rules is transferredvia a PDU session establishment accept message.
 4. The method of claim1, wherein the rule operation indicates to create new QoS rule.
 5. Themethod of claim 1, wherein the information associated with the one ormore QoS rules includes a default QoS Rule indicator (DQR) bitindicating whether the QoS rule is the default QoS rule.
 6. The methodof claim 1, wherein the PDU session modification request messagecomprises information associated with a sematic error in a QoSoperation.
 7. The method of claim 6, wherein the information associatedwith the sematic error is associated with a 5G session management (5GSM)cause #83.
 8. A network entity in a wireless communication system, thenetwork entity comprising: a transceiver; and at least one processorcoupled with the transceiver and configured to: transmit, to a userequipment (UE) via the transceiver, information associated with one ormore quality of service (QoS) rules, wherein the information associatedwith the one or more QoS rules indicates a rule operation correspondingto a QoS rule and whether the QoS rule is a default QoS rule, andwherein in case that the UE is in a narrow band (NB)-N1 mode, the ruleoperation is different from deleting existing QoS rule and the QoS ruleis not the default QoS rule, the QoS rule is detected as an error; andreceive, from the UE via the transceiver, a protocol data unit (PDU)session modification request message to delete the detected QoS rule. 9.A user equipment (UE) in a wireless communication system, the UEcomprising: a transceiver; and at least one processor coupled with thetransceiver and configured to: receive, from a network entity via thetransceiver, information associated with one or more quality of service(QoS) rules; check the information associated with the one or more QoSrules, for a QoS rule that is not a default QoS rule and for the QoSrule with a rule operation different from deleting existing QoS rule; incase that the UE is in a narrow band (NB)-N1 mode, the QoS rule is notthe default QoS rule and the rule operation is different from deletingthe existing QoS rule, detect the QoS rule as an error; and transmit, tothe network entity via the transceiver, a protocol data unit (PDU)session modification request message to delete the detected QoS rule.10. A method performed by a user equipment (UE) in a wirelesscommunication system, the method comprising: receiving, from a networkentity, information associated with one or more quality of service (QoS)flow descriptions; checking the information associated with the one ormore QoS flow descriptions, for a QoS flow description associated with anon-default QoS rule and for the QoS flow description with a flowdescription operation different from deleting the QoS flow description;in case that the UE is in a narrow band (NB)-N1 mode, a QoS flow ID(QFI) of the QoS flow description is associated with the non-default QoSrule and the flow description operation is different from deleting theQoS flow description, detecting the QoS flow description as an error;and transmitting, to the network entity, a protocol data unit (PDU)session modification request message to delete the detected QoS flowdescription.
 11. A method performed by a network entity in a wirelesscommunication system, the method comprising: transmitting, to a userequipment (UE), information associated with one or more quality ofservice (QoS) flow descriptions, wherein the information associated withthe one or more QoS flow descriptions indicates a flow descriptionoperation corresponding to a QoS flow description and a QoS flow ID(QFI) of the QoS flow description, and wherein in case that the UE is ina narrow band (NB)-N1 mode, the flow description operation is differentfrom deleting existing QoS flow description and the QFI is not the sameas a QFI of a default QoS rule, the QoS flow description is detected asan error; and receiving, from the UE, a protocol data unit (PDU) sessionmodification request message to delete the detected QoS flowdescription.
 12. The method of claim 11, wherein the informationassociated with the one or more QoS flow descriptions is transferred viaa PDU session establishment accept message, and wherein a request typeof a PDU session associated with the PDU session establishment acceptmessage is set to an initial request.
 13. The method of claim 11,wherein the flow description operation indicates to create new QoS flowdescription.
 14. The method of claim 11, wherein the PDU sessionmodification request message comprises information associated with asematic error in a QoS operation.
 15. A user equipment (UE) in awireless communication system, the UE comprising: a transceiver; and atleast one processor coupled with the transceiver and configured to:receive, from a network entity via the transceiver, informationassociated with one or more quality of service (QoS) flow descriptions;check the information associated with the one or more QoS flowdescriptions, for a QoS flow description associated with a non-defaultQoS rule and for the QoS flow description with a flow descriptionoperation different from deleting the QoS flow description; in case thatthe UE is in a narrow band (NB)-N1 mode, a QoS flow ID (QFI) of the QoSflow description is associated with the non-default QoS rule and theflow description operation is different from deleting the QoS flowdescription, detect the QoS flow description as an error; and transmit,to the network entity via the transceiver, a protocol data unit (PDU)session modification request message to delete the detected QoS flowdescription.
 16. A network entity in a wireless communication system,the network entity comprising: a transceiver; and at least one processorcoupled with the transceiver and configured to: transmit, to a userequipment (UE) via the transceiver, information associated with one ormore quality of service (QoS) flow descriptions, wherein the informationassociated with the one or more QoS flow descriptions indicates a flowdescription operation corresponding to a QoS flow description and a QoSflow ID (QFI) of the QoS flow description, and wherein in case that theUE is in a narrow band (NB)-N1 mode, the flow description operation isdifferent from deleting existing QoS flow description and the QFI is notthe same as a QFI of a default QoS rule, the QoS flow description isdetected as an error; and receive, from the UE via the transceiver, aprotocol data unit (PDU) session modification request message to deletethe detected QoS flow description.
 17. A method performed by a networkentity in a wireless communication system, the method comprising:receiving, from a user equipment (UE), information associated with anintegrity protection maximum data rate information element, wherein incase that N3 data transfer is not supported by the UE, the integrityprotection maximum data rate information element includes one or morevalues indicating that the N3 data transfer is not supported by the UE.18. The method of claim 17, wherein the one or more values indicate thatuser-plane integrity protection for a downlink is not supported by theUE.
 19. A network entity in a wireless communication system, the networkentity comprising: a transceiver; and at least one processor coupledwith the transceiver and configured to: receive, from a user equipment(UE) via the transceiver, information associated with an integrityprotection maximum data rate information element, wherein in case thatN3 data transfer is not supported by the UE, the integrity protectionmaximum data rate information element includes one or more valuesindicating that the N3 data transfer is not supported by the UE.
 20. Auser equipment (UE) in a wireless communication system, the UEcomprising: a transceiver; and at least one processor coupled with thetransceiver and configured to: in case that N3 data transfer is notsupported by the UE, identify one or more values of an integrityprotection maximum data rate information element as one or more valuesindicating that the N3 data transfer is not supported by the UE; andtransmitting, to a network entity, information associated with theintegrity protection maximum data rate information element.